Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2134

reference
68-tree-1
name
2134
tree-preservation-order

undefined

68-tpo-1
uprn
address-text
point
POINT (-0.939939 50.845656)
geometry
MULTIPOLYGON (((-0.939882 50.845650,-0.939885 50.845661,-0.939893 50.845671,-0.939905 50.845679,-0.939921 50.845684,-0.939938 50.845686,-0.939956 50.845685,-0.939972 50.845680,-0.939985 50.845672,-0.939993 50.845662,-0.939996 50.845651,-0.939993 50.845640,-0.939986 50.845630,-0.939973 50.845622,-0.939957 50.845616,-0.939940 50.845614,-0.939922 50.845616,-0.939906 50.845621,-0.939894 50.845629,-0.939885 50.845639,-0.939882 50.845650)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL